Add eTRV Monitoring, Maintenance Dropdown, and Boiler Automation Support #98
Conversation
Develop v0.7.2 release
Add dropdown to climate control dashboard card for most used maintainance operations for eTRV
|
Also added Add dropdown to climate control dashboard card for most used maintainance operations for eTRV |
Human error, added back in
genestealer
changed the title
| @@ -325,7 +325,7 @@ Both MiHome heating devices are now supported (as of v0.7.x). Specifically the | |||
| These devices are battery operated, so energenie in order to save power, have implemented periods of sleep where the devices do not listen for commands. This can lead to a delay from when a command is sent to it being processed by the device. See **Command Caching** below. | |||
|
|
|||
| ### Command Caching | |||
| Battery powered energenie devices, such as the eTRV or Thermostat do not constantly listen for commands. For example, the eTRV reports its temperature at the *SET_REPORTING_INTERVAL* (default 5 minutes) after which the receiver is then activated to listen for commands. The receiver only remains active for 200ms or until a message is received. | |||
| Battery powered energenie devices, such as the eTRV or Thermostat do not constantly listen for commands. For example, the eTRV reports its temperature at the *SET_REPORT_PERIOD* (default 5 minutes) after which the receiver is then activated to listen for commands. The receiver only remains active for 200ms or until a message is received. | |||
There was a problem hiding this comment.
Change to REPORT_PERIOD (remove SET)
|
Sorry for the delay, with Christmas and all that! I'm not entirely sure about the use of cached temperature and setting of state to show 'heating' or not; surely this is also reliant upon if the boiler has the house heating on or not? I must apologise though; I modified my code to add 'auto' on my climate nodes quite a while back, after installing the Drayton Wiser system and observing what it did; I just hadn't pushed them to 'develop' yet. 3.json: I also added an automation to set the 'heating' status for auto mode based on the boiler state using MQTT from within HA: I'll push the changes I made to develop now. |
|
Hi @Achronite,
The valve action state (heating/idle) for each valve is designed to be independent of external factors, including other valves and the heat source/boiler. This approach aligns with how other MQTT radiator valve integrations work. The retained temperature set-point in MQTT is used as it is reliably set by the app.js code when the valve is commanded to a new target temperature. This ensures consistent state determination for each valve.
The "auto" mode is not suitable for the Energenie eTRVs because these valves do not have a stored schedule. According to Home Assistant’s climate documentation, "Auto: The device is set to a schedule, learned behavior, AI." I removed all options except "heat" to simplify functionality and avoid confusion. Including "off" can also be misleading, as it suggests "valve closed," but without command caching, this could cause issues. For example:
If I understand correctly, this means setting all valve states to heating whenever the boiler is on, regardless of whether individual valves are "calling for heat" (i.e., the set-point temperature is higher than the current room temperature). This is an interesting approach and could be useful to ensure coordination between the boiler and valves. However, it diverges from the idea of each valve independently reporting its own status. Allowing valves to reflect their individual heating or idle state independently might offer more granular control, while additional logic for boiler coordination could live in Home Assistant automations. |
|
@Achronite
|
Ok. |
|
Hello @Achronite This is now tested and ready to go 😊 |
Summary
Added improved monitoring and integration for eTRVs. Key features: valve state monitoring, dropdown for maintenance commands and boiler automation support.
Changes Introduced
Why This Matters
These changes improve usability by making eTRV states and maintenance actions accessible directly from Home Assistant.
Files Updated
Example MQTT climate discovery message
{ "uniq_id": "ener314rt-4329-Climate_Control", "device": { "name": "Radiator 4329", "ids": [ "ener314rt-4329" ], "mdl": "Radiator (MIHO013) [4329]", "mf": "Energenie", "sw": "mqtt-ener314rt v0.7.2", "via_device": "mqtt-energenie-ener314rt" }, "~": "energenie/3/4329/", "name": null, "avty_t": "energenie/availability/state", "o": { "name": "mqtt-energenie-ener314rt", "sw": "v0.7.2", "url": "https://github.com/Achronite/mqtt-energenie-ener314rt" }, "curr_temp_t": "~TEMPERATURE/state", "max_temp": 40, "min_temp": 5, "modes": [ "heat" ], "mode_cmd_t": "~VALVE_STATE/command", "mode_stat_t": "~VALVE_STATE/state", "mode_cmd_tpl": "{% if value == 'off' %} 1 {% else %} 2 {% endif %}", "mode_stat_tpl": "{% if value == '1' %} off {% else %} heat {% endif %}", "temp_cmd_t": "~TARGET_TEMP/command", "temp_stat_t": "~TARGET_TEMP/state", "ic": "mdi:radiator", "opt": "true", "temp_step": "0.5", "temp_unit": "C", "act_tpl": "{% if value == 'ON' %} heating {% else %} idle {% endif %}", "act_t": "~HVAC_ACTION/state", "pr_mode_cmd_t": "~Maintenance/command", "pr_mode_stat_t": "~Maintenance/state", "pr_modes": [ "Cancel Command", "Request Diagnostics", "Request Voltage", "Exercise Valve", "Identify", "Low Power Mode ON", "Low Power Mode OFF", "Valve Auto", "Valve Open", "Valve Closed" ] }How it looks: